home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
QRZ! Ham Radio 8
/
QRZ Ham Radio Callsign Database - Volume 8.iso
/
mac
/
german
/
tcpip
/
gp160.exe
/
#TFPCR.EXE
/
TFPCR.ENG
< prev
next >
Wrap
Text File
|
1990-07-30
|
7KB
|
233 lines
Sigi Kluger, DL1MEN
Richard-Strauss-Str 19
D-8000 Munich 80
July 19, 1990 Version 1.20
DEUTSCH: TFPCR.DOC
Finally (one may brag a bit, eh?) the best packet terminal program for
the IBM PC can be forced to work with PK232, KAM, and other non-TNC2
compatibles.
How's it work?
Simple... but complicated. First, the TNC is switched to KISS mode by
some means, then TFPCR is started which will install itself in memory.
Then, SP is started.
-----------------------
ATTENTION:
This software has not been tested very thoroughly, please report any
problems to DL1MEN @ DB0PV.DEU.EU.
TFPCR assumes that a THREE-WIRE cable is used between PC and TNC.
Thus, use only pins 2, 3, and 7 (assuming a DB25 plug).
Tested with PK232 (late version), MFJ1278, and TNC2 with TF2.1c
and TAPR 1.1.6.
NOTE:
If you have a recent-version MFJ1278, please check first whether it
is TNC2-compatible. SOme 12778s have provisions for adding a WA8DED
firmware EPROM. If that is the case, the EPROM should be used rather
than TFPCR.
-----------------------
INSTALLATION:
1. SP Installation
---------------
Attention: SP version 4.01.01 or later required!
SP is to be installed in accordance with the manual and the examples
in SP.CFG. Anybody not familiar with SP should first install it using
a TNC2 with WA8DED firmware in order to practice and to minimize
problems.
At a minimum, the SP manual should be read in its entirety, taking care
to fully understand the following chapters:
- 1 to 3.6
- 4
- 5.4
- A.1
- A.10
When setting up SP.CFG, please note that SP is signalled that a TFPCR driver
is used by specifying "COM5". The baud rate for that channel may be set
to an arbitrary value since it is ignored by SP. Example:
CFG=PORT0:5
CFG=BAUD0:9600
2. Installation of TFPCR.COM:
--------------------------
TFPCR.COM must be copied into a DOS directory which is covered by
the search path.
Next, hook up the TNC and force it into KISS mode. This can be done by
TFPCR as well, but this is a function not yet fully tested.
Then, plug a radio into the TNC.
You should know the hardware port and IRQ of your COM port.
Typical values are:
COM1 -- Port 3F8 IRQ 4
COM2 -- Port 2F8 IRQ 3
TFPCR.COM defaults to COM1 9600 Baud.
The following command line parameters are supported by TF and TFPCR:
-aXXX XXX = hexadecimal Port address, e.g. -a2F8
-bNNNN NNNN = Baud rate, e.g. -b19200
-iN N = IRQ-vektor number, e.g. -i3
-s load AUTOKISS.CFG (no parameter)
-Cn n = COM-Number (1,2,3 or 4), e.g. -C1
(replaces -a and -i for standard COM addresses)
-IXX XX = interrupt vector for host, e.g. -IFE
(not supported by SP 4.01!!)
Thus, in order to start TFPCR.COM using 19200 baud and COM2, the following
is entered at the DOS prompt:
TFPCR -a2F8 -b19200 -i3
or:
TFPCR -C2 -b19200
2.1. Start of TFPCR.COM:
-------------------
TFPCR is started with the same parameters as above and sould display:
╔═══════════════════════════════════════════════════════════╗
║ TFPCR - TFPCResident v2.1c / v1.20 / INT FE / Jul 17 1990 ║
║ ║
║ RS232 Port 2F8 IRQ 3 19200 Baud 10 Chans Params at 6D01 ║
║ ║
║ TF2.1c by NORD><LINK (DF2AU/DC4OX) Changes by DL1MEN ║
╚═══════════════════════════════════════════════════════════╝
The DOS prompt should return. If the computer is crashed, reboot and check
to see whether there are any resident drivers which access the TNC COM port
or use the timer interrupt. Remove all such utilities.
TFPCR is now resident and occupies approximately 66000 bytes. The driver
may be loaded only once, refer to 4.3 (@Q) to unload the driver.
SP may now be started. For a few seconds, it should display:
TNC 0 (TF-PC/KISS) in Host mode
3. Notes:
------
TFPCR has been compiled for 10 channels.
The following TF2.1c (WA8DED) commands do not exist:
A E H K QRES Z @F
WHILE TFPCR IS LOADED, NO PROGRAM MUST BE ALLOWED TO ACCESS THE COM PORT
USED BY TFPCR!!!!!!!
During heavy packet traffic, the DOS clock may slow down quite a bit.
This is normal. Due to the heavy interrupt use, TFPCR should only be
used on ATs. TFPCR has been compiled in 286 mode and will NOT RUN
on an 8088 PC!
TFPCR may be used without a TNC connected to it.
4. Additional features:
--------------------
Two additional features still require thorough testing:
4.1. command line parameter "-s":
The -s parameter searches for a file named AUTOKISS.CFG and sends its
contents to the TNC at startup (the file is sent slowly, one character
at a time). The file must be found in the current directory, or
in the root directory of the current drive.
4.2. extended command "@K":
SP may be started without first switching to KISS mode. After startup,
enter:
ESC @K...
"..." is the command to switch into KISS mode, e.g.:
ESC @Kkiss on
or with TF2.1c:
ESC @KESC@K
(ESC = press the "ESC" key)
4.3. removing TFPCR:
The utility UNTFPC.COM removes TFPCR.COM from the system.
5. PARAMETER PATCHING
------------------
The important operating parameters may be set using DEBUG. After loading
TFPCR.COM into DEBUG, the parameters are located at the address displayed
while TFPCR is loading (6D01 in the example above). The parameters are
stored in the following sequence:
Address
("Params at"
plus offset) Bytes Default Explanation
--------------------------------------------------------------------------
0000 6 " " Call sign
0006 1 0x60 SSID (ORed with 0x60)
0007 1 4 Maximum connects
0008 1 0 DO NOT CHANGE!
0009 1 0 0=digipeat off, 1=digipeat on
000A 1 0x40 P-persistence
000B 1 0x0A Slot time
000C 1 0x1E TXDELAY
000D 1 1 1=PTT on, 0=PTT off
000E 1 1 1=AX.25 Version 2, 0=AX.25 Version 1
000F 1 4 MAXFRAME
0010 1 0x0A Number of retries
0011 1 4 FRACK
0012 1 0 Call-Validation (0=off, 1=on)
0013 1 0 0=Duplex off, 1=Duplex on
0014 1 0 DO NOT CHANGE!
0015 1 0 DO NOT CHANGE!
0016 1 0 DO NOT CHANGE!
0017 2 0x100 DO NOT CHANGE!
0019 2 0x6400 Timer T2 (decimal 100)
001B 2 0x5046 Timer T3 (decimal 18000)
001D 2 0xF802 RS232-Port (2F8)
001F 2 0x300 RS232 IRQ (3)
0021 2 0x8025 Baud rate (9600)
0023 1 0xFE Interrupt vector (DO NOT CHANGE!)